Experience with the architectural design of a modest product family
Identifieur interne : 000341 ( Main/Exploration ); précédent : 000340; suivant : 000342Experience with the architectural design of a modest product family
Auteurs : Robert W. Schwanke [États-Unis] ; Robyn R. Lutz [États-Unis]Source :
- Software: Practice and Experience [ 0038-0644 ] ; 2004-11-10.
English descriptors
- KwdEn :
Abstract
Many product families are modest in the sense that they consist of a sequence of incremental products with, at any point in time, only a few distinct products available and minimal variations among the products. Such product families, nevertheless, are often large, complex systems, widely deployed, and possessing stringent safety and performance requirements. This paper describes a case study that tends to confirm the value of using a product‐line approach for the architectural design of a modest product family. The paper describes the process, design alternatives, and lessons learned, both positive and negative, from the architectural design of one such family of medical image analysis products. Realized benefits included identifying previously unrecognized common behavior and sets of features that were likely to change together, aligning the architecture with specific market needs and with the organization, and reducing unplanned dependencies. Most interesting were the unanticipated benefits, including decoupling the product‐family architecture from the order of implementation of features, and using the product‐family architecture as a ‘guiding star’ with subsequent releases moving toward, rather than away from, the planned architecture. Copyright © 2004 John Wiley & Sons, Ltd.
Url:
DOI: 10.1002/spe.613
Affiliations:
Links toward previous steps (curation, corpus...)
Le document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">Experience with the architectural design of a modest product family</title><author><name sortKey="Schwanke, Robert W" sort="Schwanke, Robert W" uniqKey="Schwanke R" first="Robert W." last="Schwanke">Robert W. Schwanke</name></author><author><name sortKey="Lutz, Robyn R" sort="Lutz, Robyn R" uniqKey="Lutz R" first="Robyn R." last="Lutz">Robyn R. Lutz</name></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:0C1DAD9A7CC47D415BF2B5BB0C8039FAF954508E</idno><date when="2004" year="2004">2004</date><idno type="doi">10.1002/spe.613</idno><idno type="url">https://api.istex.fr/document/0C1DAD9A7CC47D415BF2B5BB0C8039FAF954508E/fulltext/pdf</idno><idno type="wicri:Area/Main/Corpus">000567</idno><idno type="wicri:Area/Main/Curation">000567</idno><idno type="wicri:Area/Main/Exploration">000341</idno><idno type="wicri:explorRef" wicri:stream="Main" wicri:step="Exploration">000341</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">Experience with the architectural design of a modest product family</title><author><name sortKey="Schwanke, Robert W" sort="Schwanke, Robert W" uniqKey="Schwanke R" first="Robert W." last="Schwanke">Robert W. Schwanke</name><affiliation wicri:level="1"><country xml:lang="fr">États-Unis</country><wicri:regionArea>Siemens Corporate Research Inc., 755 College Road East, Princeton, NJ 08540‐6632</wicri:regionArea><wicri:noRegion>NJ 08540‐6632</wicri:noRegion></affiliation></author><author><name sortKey="Lutz, Robyn R" sort="Lutz, Robyn R" uniqKey="Lutz R" first="Robyn R." last="Lutz">Robyn R. Lutz</name><affiliation wicri:level="4"><country xml:lang="fr">États-Unis</country><wicri:regionArea>Department of Computer Science, Iowa State University, Ames, IA 50011‐1041, U.S.A. and Jet Propulsion Laboratory/Caltech, Pasadena, CA 91109</wicri:regionArea><orgName type="university">Université d'État de l'Iowa</orgName><placeName><settlement type="city">Ames (Iowa)</settlement><region type="state">Iowa</region></placeName></affiliation></author></analytic><monogr></monogr><series><title level="j">Software: Practice and Experience</title><title level="j" type="abbrev">Softw: Pract. Exper.</title><idno type="ISSN">0038-0644</idno><idno type="eISSN">1097-024X</idno><imprint><publisher>John Wiley & Sons, Ltd.</publisher><pubPlace>Chichester, UK</pubPlace><date type="published" when="2004-11-10">2004-11-10</date><biblScope unit="volume">34</biblScope><biblScope unit="issue">13</biblScope><biblScope unit="page" from="1273">1273</biblScope><biblScope unit="page" to="1296">1296</biblScope></imprint><idno type="ISSN">0038-0644</idno></series><idno type="istex">0C1DAD9A7CC47D415BF2B5BB0C8039FAF954508E</idno><idno type="DOI">10.1002/spe.613</idno><idno type="ArticleID">SPE613</idno></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">0038-0644</idno></seriesStmt></fileDesc><profileDesc><textClass><keywords scheme="KwdEn" xml:lang="en"><term>medical image analysis</term><term>modest product family</term><term>product line architecture</term><term>software architecture</term><term>software product family</term><term>software product line</term></keywords></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">Many product families are modest in the sense that they consist of a sequence of incremental products with, at any point in time, only a few distinct products available and minimal variations among the products. Such product families, nevertheless, are often large, complex systems, widely deployed, and possessing stringent safety and performance requirements. This paper describes a case study that tends to confirm the value of using a product‐line approach for the architectural design of a modest product family. The paper describes the process, design alternatives, and lessons learned, both positive and negative, from the architectural design of one such family of medical image analysis products. Realized benefits included identifying previously unrecognized common behavior and sets of features that were likely to change together, aligning the architecture with specific market needs and with the organization, and reducing unplanned dependencies. Most interesting were the unanticipated benefits, including decoupling the product‐family architecture from the order of implementation of features, and using the product‐family architecture as a ‘guiding star’ with subsequent releases moving toward, rather than away from, the planned architecture. Copyright © 2004 John Wiley & Sons, Ltd.</div></front></TEI><affiliations><list><country><li>États-Unis</li></country><region><li>Iowa</li></region><settlement><li>Ames (Iowa)</li></settlement><orgName><li>Université d'État de l'Iowa</li></orgName></list><tree><country name="États-Unis"><noRegion><name sortKey="Schwanke, Robert W" sort="Schwanke, Robert W" uniqKey="Schwanke R" first="Robert W." last="Schwanke">Robert W. Schwanke</name></noRegion><name sortKey="Lutz, Robyn R" sort="Lutz, Robyn R" uniqKey="Lutz R" first="Robyn R." last="Lutz">Robyn R. Lutz</name></country></tree></affiliations></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Amerique/explor/CaltechV1/Data/Main/Exploration
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000341 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Main/Exploration/biblio.hfd -nk 000341 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Amerique
|area= CaltechV1
|flux= Main
|étape= Exploration
|type= RBID
|clé= ISTEX:0C1DAD9A7CC47D415BF2B5BB0C8039FAF954508E
|texte= Experience with the architectural design of a modest product family
}}
| This area was generated with Dilib version V0.6.32. |  |